…#257)

## What

`Verify Global Install` workflow hardcoded `MAX_INSTALL_SECS: "60"`, but
`scripts/verify-global-install.sh` documents a **120s** default and its
header explicitly notes the tight 60s *"tripped on slow cells despite a
clean install."* This change deletes the override so the workflow uses
the script's documented 120s ceiling.

## Why

The `macos-x64-node24-nvm` leg flaked on the last release push (`chore:
release main #256`, `4c16f5b`):

```
[FAIL] gate 4: install took 61s (> 60s budget)
```

A **1-second** margin miss on a clean install — not a regression. The
CI, CodeQL, Semgrep, Self-Scan, and Scorecard suites all passed on the
same SHA; only this timing gate tripped.

The gate exists to catch an install that **hangs or refetches** the
native prebuilts (ladybug + duckdb + onnxruntime — though note ADR 0019
has since removed ladybug/duckdb, leaving onnxruntime-node as the only
native dep). On a loaded shared macOS runner a cold-cache global install
legitimately varies 30–90s, so 60s was below the noise floor. 120s keeps
the hang-detection intent while ending the margin flakes.

## Blast radius

CI-only. One env value in one workflow step. No source or runtime
change.

Fixes the recurring macOS-runner flake class tracked in #163.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>